Permit Compliance System

ABSTRACT

A system and method is disclosed that enables the display of permits and/or permit information related to a specific location, collection of permitting data onsite, comparison of the onsite data to permitted constraints, and reporting the results of the inspection (as required under the appropriate regulatory policy or as requested by the organization or entity being inspected), as well as sending immediate notifications, as appropriate, to decision makers. In certain embodiments, the system and method may also offer predictions on the likelihood of an enforcement action against the organization given factors such as, but not limited to, the type of violation, degree of violation, and enforcement actions against others for similar violations. In other embodiments, the system and method allows the permittee to mitigate the risk of a violation by notifying emergency personnel in addition to decision makers within the organization.

RELATED APPLICATIONS

This application claims the benefit of priority of U.S. ProvisionalPatent Application No. 51/863,461 filed Aug. 8, 2013, and titled “PermitCompliance System”, which is incorporated by reference in its entirety.

FIELD OF THE INVENTION

The present invention generally relates to monitoring and reportingsystems. In particular, the present invention is directed to a permitcompliance system.

BACKGROUND

Compliance officers, such as environmental compliance officers,typically gather information about effluents, emissions, exhausts, etc.,coming from a plant or facility based on issued permits from state,federal, or local agencies for that plant or facility. For certainorganizations, especially those with multiple sites in variousjurisdictions, the permitting requirements may vary widely, thusrequiring the compliance officer to negotiate the differences betweeneach permitted site as the officer travels from site to site collectingthe information needed for the particular reporting they do(environmental compliance, construction compliance, safety inspections,and any other location-based reporting). After collecting theinformation, the compliance officer will return to their office toreport the data and, at least in the case of environmental permits,compare the data to the permitted effluent/exhaust limitations. Oncereported and compared, the data may need to be reported to the relevantagency, and in the case of a violation or potential or possibleviolation, the information also needs to be transmitted to a responsibleparty/decision maker.

As is evident, the process of obtaining, recording, comparing, andtransmitting compliance data is prone to inaccuracies, fraudulentactivities, and delays that may put the organization or human lives atrisk. Furthermore, there is no ability to audit when and where the datawas collected, i.e., the actual GPS location and the date and time onwhich the data was gathered, and if all the data was collected at thesame time. As such, there is no way to guarantee that the inspection wasactually performed on-site (i.e., at a location that was part of thesite inspection) or was manipulated to avoid compliance issues. Due tothe significant opportunities for error and/or outright fraud in thecurrent methods for collecting and processing inspection data, companiesare at risk for possible penalties and fines for noncompliance or fornot responding quickly (enough) to problem areas.

SUMMARY OF THE DISCLOSURE

In a first exemplary aspect there is disclosed a permit compliancesystem for monitoring a sites compliance with one or more permitslimiting or controlling the activities and/or discharges from the site,the permit compliance system comprising a mobile compliance devicehaving a processor and a non-transitory computer readable medium incommunication with the processor, wherein the non-transitory computerreadable medium includes: an input module configured to: determine alocation of the mobile compliance device and one or more permitlimitations related to the location, wherein each of the one or morepermit limitations includes a permitted discharge value; and receivedata for each of the one or more permit limitations representing anactual discharge; a comparison module configured to determine adifference between the actual discharge with the permitted dischargevalue; and a prediction module configured to determine a likelihood ofan enforcement action based upon the difference.

In another exemplary aspect there is disclosed a permit compliancesystem for monitoring, reporting, and complying with permit limitationsrelated to a site or a permitted discharge, the permit compliance systemcomprising a mobile compliance device having a processor and anon-transitory computer readable medium in communication with theprocessor, the mobile compliance device configured to receiveinformation related to a discharge; a database in communication with themobile compliance device, the database including: one or more permitsrelated to the site or the permitted discharge; records relating to pastdischarge activity at the site; and compliance credits earned or ownedby the site; a reporting system in communication with the mobilecompliance device and the database, the reporting system configured to:determine a discharge event; determine remedial steps based on thedischarge event; transmit information related to the discharge event andthe remedial steps.

In yet another exemplary aspect there is disclosed a method of limitingan organization's exposure to violations of a permit having permitteddischarge values comprising receiving, as an input, information relatedto a discharge at the organization; comparing the discharge to thepermitted discharge value contained within the permit regulating theorganization; determining the extent to which the discharge exceeds thepermitted discharge; predicting a risk value by evaluating thedetermining in conjunction with one or more of: a number of exceededpermit limitations; the extent; an amount of time the extent; a toxicityor dangerousness of the extent; how often enforcement actions are takenagainst industries related to the organization; how often theorganization has had an enforcement action brought against it; number ofenforcement actions in the surrounding geographical area; number ofenforcement actions taken in that jurisdiction for similarnoncompliance; cost of enforcement actions for similar noncompliance asthe extent; and the speed with which the organization remedies theextent; and minimizing the organization's exposure based upon theevaluating.

BRIEF DESCRIPTION OF THE DRAWINGS

For the purpose of illustrating the invention, the drawings show aspectsof one or more embodiments of the invention. However, it should beunderstood that the present invention is not limited to the precisearrangements and instrumentalities shown in the drawings, wherein:

FIG. 1 is a schematic representation of an information system for usewith a permit compliance system (PCS) according to an embodiment of thepresent invention;

FIG. 2 is a block diagram of a PCS according to an embodiment of thepresent invention;

FIGS. 3A-3C are schematics of a mobile device for use with a PCSaccording to an embodiment of the present invention;

FIG. 4 is a flow diagram of a method of conducting permit complianceaccording to embodiment of the present invention; and

FIG. 5 is a schematic representation of a computer system suitable foruse with the PCS according to an embodiment of the present invention.

DESCRIPTION OF THE DISCLOSURE

A permit compliance system (PCS) according to the present disclosureenables the display of permits and/or permit information related to aspecific location, collection of permitting data onsite, comparison ofthe onsite data to permitted constraints, and reporting the results ofthe inspection (as required under the appropriate regulatory policy oras requested by the organization or entity being inspected), as well assending immediate notifications, as appropriate, to decision makers. Incertain embodiments, a PCS according to the present disclosure may alsooffer predictions on the likelihood of an enforcement action against theorganization given factors such as, but not limited to, the type ofviolation, degree of violation, and enforcement actions against othersfor similar violations. In other embodiments, a PCS according to thepresent disclosure allows the permittee to mitigate the risk of aviolation by notifying emergency personnel in addition to decisionmakers within the organization.

Turning now to the figures, FIG. 1 schematically illustrates anembodiment of a system 100 used facilitate that operation of a PCS 200(depicted in FIG. 2 and discussed below). System 100 may be used tocommunicate a wide variety of information within and external to PCS 200including, but not limited to, permit information, compliance officerpreferences, compliance officer situational factors, including time,date, weather, and compliance officer location.

System 100 may include a computing device 104, an information network108, (such as the Internet), a local area network 112, a content source116, and one or more mobile devices 120. Computing device 104 and mobiledevices 120 may communicate through information network 108 (and/orlocal area network 112) in order to access information in content source116. Content source 116 can be, for example, a non-transitory machinereadable storage medium, a database, whether publicly accessible,privately accessible, or accessible through some other arrangement suchas subscription, that holds permit related information, data, programs,algorithms, or computer code, thereby accessible by computing device104, mobile devices 120, and PCS 200. Content source 116 can be updatedor modified to include new or additional permit information, such asadditional requirements, updated limitations, and the like. In anexemplary embodiment, permit information contained on content source 116is not updatable or modifiable except by certain personnel and may onlybe accessible via a separate computing device 104 that is not availableor accessible to the compliance officer.

As those skilled in the art will appreciate, computing device 104 maytake a variety of forms, including, but not limited to, a web appliance,a laptop computer, a desktop computer, a computer workstation, aterminal computer, web-enabled televisions, media players, and othercomputing devices in communication with information network 108.

Information network 108 may be used in connection with system 100 toenable communication between the various elements of the system. Forexample, as indicated in FIG. 1, information network 108 may be used bycomputing device 104 to facilitate communication between content source116 and the computing device, as well as mobile devices 120. Thoseskilled in the art will appreciate that computing device 104 may accessinformation network 108 using any of a number of possible technologiesincluding a cellular network, WiFi, wired internet access, combinationsthereof, as well as others not recited, and for any of a number ofpurposes including, but not limited to, those reasons recited above.

As locations needing permit compliance may be relatively inaccessible bywireless transmissions, in an exemplary embodiment one or more of themodules included with PCS 200 (discussed in detail below with referenceto FIG. 2) reside on computing device 104 or mobile devices 120. Thisconfiguration can allow a compliance officer to freely move throughoutthe facility to capture the appropriate information and to later uploadthe relevant data when connected to information network 108.Alternatively, communication between the modules included with PCS 200may be initiated through a webpage instantiated in a web-basedenvironment existing that is accessible through an information network,such as network 108. In this embodiment, if wireless Internet access isavailable, then the data may be transmitted to a database residing on aserver. If wireless Internet access is not available, then the data canbe saved locally (i.e., on computing device 104) until such time thatwireless Internet access is available and/or the compliance officerattempts to send the saved data or a collection of saved data back tothe server.

As noted above, PCS 200 includes one or more software modules configuredto allow for the recall of permit information based on the location ofthe compliance officer; the input of emission, effluent, exhaust,discharge, or other permit monitoring requirements by the complianceofficer via a computing device 104; the comparison of the inputinformation to permit limitations; notification to decision makers basedupon the comparison; and a prediction of possible enforcement action asa function of various factors. To simplify and control the recording ofpermit information, one or more of the modules included with PCS 200determines the appropriate input based upon the place that thecompliance officer is at. The location of the place may be anygeolocatable position, but is generally associated with the structure,building, land, etc. that is subject to the permit.

In the exemplary embodiment shown in FIG. 2, PCS 200 includes an inputmodule 204, a geolocation module 208, a comparison module 212, aprediction module 216, and a reporting module 220. Input module 204allows for inputting input data, e.g., monitoring information or values,from a compliance officer into PCS 200. Input data may include, but isnot limited to, readings taken from a gauge, physical condition of acomponent, an environment defined as a safety issue, etc. In thisembodiment, when PCS 200 is implemented using computing device 104,which can be, for example, a laptop computer, a desk top computer, atablet, or other computing device capable of connecting to the Internet,input module 204 permits a compliance officer to input permit relatedinformation such as, but not limited to, those found in the followingtables:

A.1 During the period beginning on the effective date and lastingthrough expiration, the permittee is authorized to discharge treatedwastewater from outfall 001 to an unnamed tributary to the BlackstoneRiver. Such discharges shall be limited and monitored by the permitteeas specified below. EFFLUENT EFFLUENT LIMITS MONITORING REQUIREMENTS²CHARACTERISTIC AVERAGE AVERAGE AVERAGE AVERAGE MAXIMUM MEASUREMENTSAMPLE PARAMETER MONTHLY WEEKLY MONTHLY WEEKLY DAILY FREQUENCY TYPEFLOW¹ **** **** 2.0 MGD **** Report MGD CONTINUOUS RECORDER FLOW¹ ******** Report MGD **** *** CONTINUOUS RECORDER BOD₅ ³ 167 lbs/Day 167lbs/Day 10 mg/l 10 mg/l Report mg/l 3/WEEK 24-HR COMPOSITE⁴ TSS ³ 167lbs/Day 167 lbs/Day 10 mg/l 10 mg/l Report mg/l 3/WEEK 24-HR COMPOSITE⁴pH Range⁵ 6.5-8.3 SU (SEE PERMIT PARAGRAPH I.A.1.b.) 1/DAY GRABESCHERICHIA COLI ^(5,6) **** **** 126 cfu/100 ml *** 409 cfu/100 ml3/WEEK GRAB (April 1 to October 31) ENTEROCOCCI ^(6,7) **** **** 108cfu/100 ml **** 350 cfu/100 ml 1/WEEK GRAB TOTAL COPPER **** ****   22ug/l ****   32 ug/l 1/MONTH 24-HR COMPOSITE⁴ TOTAL ZINC **** ****   58ug/l ****   58 ug/l 1/MONTH 24-HR COMPOSITE⁴ TOTAL LEAD⁸ **** ****  0.9ug/l **** Report ug/l 1/MONTH 24-HR COMPOSITE⁴ TOTAL CADMIUM⁸ **** ****0.16 ug/l **** 0.94 ug/l 1/MONTH 24-HR COMPOSITE⁴ TOTAL ALUMINUM ********   87 ug/l ****  844 ug/l 1/MONTH 24-HR COMPOSITE⁴ DISSOLVED OXYGEN⁵NOT LESS THAN 5.0 mg/l 1/DAY GRAB (April 1^(st)-October 31^(st))

A.1 During the period beginning the effective date and lasting throughexpiration, the permittee is authorized to discharge treated wastewaterfrom outfall 001 to an unnamed tributary to the Blackstone River. Suchdischarges shall be limited and monitored by the permittee as specifiedbelow. EFFLUENT EFFLUENT LIMITS MONITORING REQUIREMENTS² CHARACTERISTICAVERAGE AVERAGE AVERAGE AVERAGE MAXIMUM MEASUREMENT SAMPLE PARAMETERMONTHLY WEEKLY MONTHLY WEEKLY DAILY FREQUENCY TYPE AMMONIA-NITROGEN 33.4lbs/ 66.7 lbs/Day   2 mg/l  4 mg/l Report mg/l 1/WEEK 24-HR COMPOSITE⁴(May 1-October 31) Day    AMMONIA-NITROGEN  150 lbs/  300 lbs/Day   9mg/l 18 mg/l Report mg/l 1/WEEK 24-HR COMPOSITE⁴ (November 1-April 30)Day TOTAL PHOSPHORUS¹³  3.3 lbs/ **** 0.2 mg/l **** Report mg/l 2/WEEK24-HR COMPOSITE⁴ (April 1-October 31) Day TOTAL PHOSPHORUS¹³ 16.7 lbs/**** 1.0 mg/l **** Report mg/l 2/MONTH 24-HR COMPOSITE⁴ (November1-March 31) Day ORTHO PHOSPHORUS¹³ Report **** Report mg/l **** Reportmg/l 2/MONTH 24-HR COMPOSITE⁴ (November 1-March 31) lbs/Day TOTALNITROGEN¹⁴  133 lbs/ ****   8 mg/l **** Report mg/l 1/WEEK 24-HRCOMPOSITE⁴ (May 1-October 31) Day TOTAL KJELDAHL Report lbs/ **** Reportmg/l **** Report mg/l 1/WEEK 24-HR COMPOSITE⁴ NITROGEN Day TOTALNITRATE + Report lbs/ **** Report mg/l **** Report mg/l 1/WEEK 24-HRCOMPOSITE⁴ NITRATE Day WHOLE EFFLUENT Acute LC50 ≧ 100% 4/YEAR 24-HRCOMPOSITE⁴ TOXICITY ^(9, 10, 11, 12) Chronic C-NOEC ≧ 83% Hardness¹⁵ ****** *** *** Report mg/l 4/YEAR 24-HR COMPOSITE⁴ Ammonia Nitrogen as N¹⁵*** *** *** *** Report mg/l 4/YEAR 24-HR COMPOSITE⁴ Total RecoverableAluminum¹⁵ *** *** *** *** Report mg/l 4/YEAR 24-HR COMPOSITE⁴ TotalRecoverable Cadmium¹⁵ *** *** *** *** Report mg/l 4/YEAR 24-HRCOMPOSITE⁴ Total Recoverable Copper¹⁵ *** *** *** *** Report mg/l 4/YEAR24-HR COMPOSITE⁴ Total Recoverable Nickel¹⁵ *** *** *** *** Report mg/l4/YEAR 24-HR COMPOSITE⁴ Total Recoverable Lead¹⁵ *** *** *** *** Reportmg/l 4/YEAR 24-HR COMPOSITE⁴ Total Recoverable Zinc¹⁵ *** *** *** ***Report mg/l 4/YEAR 24-HR COMPOSITE⁴

In an exemplary embodiment, input module 204 presents only one or a fewmonitoring requirements to the compliance officer at a time so as tosimplify compliance with reporting and limit the ability of thecompliance officer to inadvertently miss any one measurement. Inputmodule 204 may also be configured such that the compliance officercannot “skip” the input of required monitoring information. Thisconfiguration avoids the possibility of incomplete reporting. In thisembodiment, and to enable the compliance officer to continue reportingin the instance in which a piece of monitoring equipment ismalfunctioning or a value cannot be obtained in order to report, inputmodule 204 may include an override control that permits non-entry ofdata under certain conditions. Input module 204 may also be configuredsuch that input module will not allow a compliance officer to enter ormodify input data related to a permit requirement of a permitted siteunless the compliance officer is at the site. This configurationminimizes the opportunity for later revision or entering of an inputdata and thus possible fraud.

Input module 204 may also allow the compliance offer to designate ageolocatable place as a location, which may be useful for, for example,if the facility has multiple building sites which makes automaticrecognition difficult or to indicate a precise location of a possibletrouble area. The compliance officer may select or designate thelocation using computing device 104 by ways known in the art, such as,but not limited to, touching a spot on a touchscreen, voicing a command,directing a trackball, or using other devices in combination with acomputer-based map program. For example, a compliance officer maydesignate the geolocatable place on the map program that is displayed oncomputing device 104 by moving an indicator of the program to thelocation of the place on the map, and registering the geolocation byclicking a mouse button, voicing the appropriate command, pressing thetouchscreen, or otherwise so indicating his/her present location.

Input module 204 may also allow a compliance officer to include otherrelated information to the geolocatable place. For example, a complianceofficer may input a time of arrival at the place, an experience thecompliance officer had at the place, the type of event occurring at theplace, and the like. A person of ordinary skill in the art shouldunderstand that some examples of the aforementioned pieces of relatedinformation may be generated automatically when the compliance officerdesignates geolocatable place. For example, if the compliance officerdesignates a geolocatable place on computing device 104, e.g., bytapping a compliance officer interface element (such as a touchscreendisplaying a map program) with a command such as “Record This,” thecomputing device may concomitantly record a time-stamp associated withthe designation. The data input by a compliance officer into inputmodule 204 may be stored in a database (described further below withreference to FIG. 5) for later retrieval or processing.

Geolocation module 208, in an exemplary embodiment, is configured toautomatically identify the location of the compliance officer, or actupon the request of the compliance officer via input module 204, so asto identify and/or record the location of a place, which in someembodiments may be a pair of coordinates (i.e., latitudinal andlongitudinal) representative of a current location of the complianceofficer, an address of a business, a building site, or other addressableor geolocatable place. It should be appreciated by those of ordinaryskill in the art that location information may be obtained in a numberof different ways. For example, location information may be identifiedusing a mapping program, Internet-based or otherwise, IP address of acomputer or wireless network, and other known means. In an exemplaryembodiment, the location of the device (e.g., mobile device 120)indicates to PCS 200 which site, building, or location the complianceofficer is at and the front-end application presents to the complianceofficer, based upon his/her location, the items that require inspectionat that time.

In an embodiment, computing device 104 (FIG. 1) includes technology fordetermining an address of an indicated place or ascertaining informationassociated with the indicated place using geolocation module 208.Computing device 104 can then communicate that information to anotherentity, or another entity may retrieve that data from the computingdevice. When computing device 104 communicates with another device (suchas mobile device 120), the computing device is associated withidentifying information such as addressing information, presenceinformation, and the like. For example, computing device 104 can becomeassociated with an internet protocol (IP) address, a MAC address, anetwork port, or any number of other types of addressing or locatinginformation. IP addresses, MAC addresses, and others may be analyzed toascertain information about the location of the computing device 104.Alternatively, computing device 104 can utilize an address associatedwith an internet service provider, a local area network, and the like.

PCS 200 can also compare the values input by the compliance officer orautomatically received via a piece of monitoring equipment to limits inthe appropriate permit via comparison module 212. In an exemplaryembodiment, comparison module 212 determines the extent to which apermitted variable is exceeded. For example, if the permitted dischargefor a given effluent source is X/gal/min, comparison module 212 candetermine that a discharge rate of 2X/gal/min is two times the regulatedlimit. Comparison module 212 may also be designed and configured to docomplex calculations required by the permit prior to comparing theinputted monitoring data with the permitted value. The output ofcomparison module 212 is comparison data that, depending on the value,can be transmitted for further action. For example, and as described inmore detail just below, comparison data may be provided to predictionmodule 216 for further evaluation. Alternatively, comparison module 212may, upon determining a possible violation (e.g., discharge abovepre-determined parameters), transmit a warning or notice of the possibleinfraction to a decision maker, such as, but not limited to, in-housecounsel, outside counsel, or a third-party response organization. Inanother embodiment, if noncompliance is determined by comparison module212, a check-list or other representation of best practices/procedures(either preprogrammed or garnered from a third-party resource such as anenvironmental response firm) for dealing with the compliance issue maybe presented to the compliance officer, who may then be able to addressthe noncompliance issue directly.

Prediction module 216 evaluates the comparison data from comparisonmodule 212 and input module 204 and determines the likelihood of anenforcement action. Prediction module 216 may use several factorsincluding, but not limited to or confined by, 1) the number of monitoredparameters exceeded, 2) how severe the monitored parameter was exceeded(double, triple, etc.), 3) amount of time the aforementioned monitoredparameters have been exceeded, 4) toxicity or dangerousness of themonitored parameter exceeded, 4) how often enforcement actions are takenagainst the relevant industry, 5) how often this particular permitteehas had an enforcement action brought against them, 7) number ofenforcement actions in the surrounding geographical area, 8) number ofenforcement actions taken in that jurisdiction for similarnoncompliance, 9) cost of enforcement actions for similar noncompliance(which could be a separate feature on its own), and 10) the speed withwhich noncompliance of this permittee in this instance was remedied.

The information used by prediction module 216 can come from a number ofsources and databases. For example, information about a specific sitemay be complied within a database (not shown) of input data andcomparison data that is kept by the permittee. Other information may beretrieved from public sources of information, such as, but not limitedto, the U.S. Environmental Protection Agency's Enforcement andCompliance History Online (ECHO) Database.

After input data is evaluated by comparison module 212 and predictionmodule 216 (when implemented), relevant reports and or notifications maybe delivered by reporting module 220. Reporting module 220 may allow forsorting, filtering, and displaying the data, comparisons, data trends,and alternative predications, as desired. If notifications are requiredbased upon pre-determined criteria (either permit required or permitteerequested), a notification can be immediately transmitted to theappropriate parties, including, but not limited to, an appropriateregulatory agency, a decision maker, and emergency personnel.

Reporting module 220 can include an authentication module 224.Authentication module 224 includes those standards and requirements thatare necessary for the submission of reports in compliance with aregulatory agency (e.g., Environmental Protection Agency). In anembodiment of PCS 200, authentication module 224 may accompany a reportof the compliance data generated by reporting module 220 when the reportis delivered to a decision maker with the responsibility of submittingdata to the regulatory agency. In this embodiment, the decision makercan, after reviewing the report, use authentication module 224 to submitthe compliance data to the agency. Reporting module 220 may also beconfigured to allow for internal compliance audits. Moreover, and ifdesired, some or all of the data reportable by reporting module 220 maybe available to outside entities. For example, an organization maychoose to make its compliance history publically available andsearchable by location.

One or more of the modules discussed herein may also be configured todetermine the availability of any unused discharge credits nearby andsuggest the purchase and or sale of credits (while still remaining inoverall compliance, for example, remaining in compliance with the WaterQuality Standard for that water body and the TMDL (Total Maximum DailyLoad) if one has been set for that water body). This information may betransmitted to the decision maker along with any report or notice ofnoncompliance so that the decision maker has a fuller understanding ofhis/her available optioning in addressing discharge situations. In anexemplary embodiment, the decision maker can purchase or selldischarge/emission credits possessed by other permitted entities usingPCS 200, by for example, communicating via system 100. For example, if apermitted entity has unused discharge/emission credits, the decisionmaker may offer for sale those unused credits through system 100. If apermitted entity has exceeded its discharge/emission parameters, forexample, when notified by comparison module 208, the permitted entitymay purchase credits from those offering credits for sale. Accordingly,decision makers can buy and sell credits after receiving notifications,after reporting non-compliance, after authenticating the data transferas described above, and at other times. In another exemplary embodiment,PCS 200 may determine to whom unused credits should be offered for salebased upon the location of the permit, thereby facilitating the transferof credits among similarly situated permitted entities. In thisembodiment, PCS 200 may display the credits in a reporting module(similar to reporting module 220) of other similarly situated permittedentities, enabling an otherwise out of compliance permitted entity toattain compliance by purchasing unused credits from other permittedentities within an appropriate geographical area. The entire transactionbetween permitted entities may take place within PCS 200 by linkingfinancial accounts so that payment can be debited and credited to theappropriate parties at the time of the transaction. Alternatively, anescrow account may be established so that money is placed by permittedentities from which credit purchases can be debited, and credit salescan be added.

Turning now to FIGS. 3A-C, there is shown an implementation of a mobiledevice 120 (FIG. 1) suitable for use with PCS 200. Mobile device 120 caninclude a touch-sensitive display 304, an input device 308, a speaker312, and a transceiver 316. Touch-sensitive display 304 is sometimescalled a “touch screen” for convenience, and may also be known as orcalled a touch-sensitive display system. Touch screen 304 can be used todisplay information or to provide compliance officer-interface objects320 (e.g., virtual (also called “soft”) control keys, such as buttons orkeyboards), thereby providing an input interface and an output interfacebetween mobile device 120 and a compliance officer. Informationdisplayed by touch screen 304 can include graphics, maps, text, icons,video, and any combination thereof (collectively termed “graphics”). Inan embodiment, and in use with PCS 200, a compliance officer can selectone or more compliance officer-interface objects 320, e.g., object 320′,using touch screen 304 to designate that mobile device 120 is at theappropriate location.

Touch screen 304 has a touch-sensitive surface, which uses a sensor orset of sensors to accept input from the compliance officer based onhaptic and/or tactile contact. Touch screen 304 may use LCD (liquidcrystal display) technology, or LPD (light emitting polymer display)technology, although other display technologies may be used in otherembodiments. Touch screen 304 can detect contact (and any movement orbreaking of the contact) on the touch screen and converts the detectedcontact into interaction with compliance officer-interface objects(e.g., one or more soft keys, icons, web pages or images) that aredisplayed on the touch screen. Touch screen 304 may detect contact andany movement or breaking thereof using any of a plurality of touchsensing technologies now known or later developed, including but notlimited to capacitive, resistive, infrared, and surface acoustic wavetechnologies, as well as other proximity sensor arrays or other elementsfor determining one or more points of contact with a touch screen 304.In an exemplary embodiment of the use of mobile device 120, a complianceofficer presses a finger to touch screen 304 so as to initiate contact.In alternative embodiments, a compliance officer may make contact withtouch screen 304 using any suitable object, such as, but not limited to,a stylus.

Input device 308 facilitates navigation among and interacts with one ormore compliance officer-interface objects 320 displayed in the touchscreen 304. In an embodiment, input device 308 is a click wheel that canbe rotated or moved such that it can be used to select one or moreuser-interface objects 320 displayed on touch screen 304. In analternative embodiment, input device 308 can be a virtual click wheel,which may be either an opaque or semitransparent object that appears anddisappears on the touch screen display in response to compliance officerinteraction with mobile device 120.

Transceiver 316 receives and sends signals from mobile device 120. In anembodiment of mobile device 120, transceiver 316 sends and receivesradio frequency signals through one or more communications networks,such as network 108 (FIG. 1), and/or other computing devices, such ascomputing device 104. Transceiver 316 may be combined with well-knowncircuitry for performing these functions, including, but not limited to,an antenna system, one or more amplifiers, a tuner, one or moreoscillators, a digital signal processor, a CODEC chipset, a subscriberidentity module (SIM) card, and a memory. As mentioned above,transceiver 316 may communicate with one or more networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN), and/or a metropolitan area network(MAN), and other devices. Mobile device 120 may use any of a pluralityof communications standards to communicate to networks or other deviceswith transceiver 316. Communications standards, protocols andtechnologies for communicating include, but are not limited to, GlobalSystem for Mobile Communications (GSM), Enhanced Data GSM Environment(EDGE), high-speed downlink packet access (HSDPA), wideband codedivision multiple access (W-CDMA), code division multiple access (CDMA),time division multiple access (TDMA), Bluetooth, Wireless Fidelity(Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g and/or IEEE802.11n), voice over Internet Protocol (VoIP), Wi-MAX, a protocol foremail (e.g., Internet message access protocol (IMAP) and/or post officeprotocol (POP)), instant messaging (e.g., extensible messaging andpresence protocol (XMPP), Session Initiation Protocol for InstantMessaging and Presence Leveraging Extensions (SIMPLE), and/or InstantMessaging and Presence Service (IMPS)), and/or Short Message Service(SMS)), or any other suitable communication protocol.

Transceiver 316 may also be configured to assist mobile device 120 indetermining its current location. For example, geolocation module 208(FIG. 2) can direct transceiver 316 to provide signals that are suitablefor determining the location of mobile device 120, as discussed indetail above. As shown in FIG. 3A, mobile device 120 can indicate thatit is searching for the current location and relevant permittinginformation (e.g., interface object 320′). Mobile device can alsorequest input from the compliance officer as to whether or not it hasidentified the correct location at interface object 320″. The complianceofficer can then indicate, using touch-screen 304 or other means, suchas voice activation, that the geolocation module 208 has identified theappropriate location.

Mobile device 120 may also include other applications or programs suchas, but not limited to, word processing applications, JAVA-enabledapplications, encryption, digital rights management, voice recognition,voice replication, and a browser module. The browser module may be usedto browse the Internet, including searching, linking to, receiving, anddisplaying web pages or portions thereof, as well as attachments andother files linked to web pages.

It should be appreciated that the mobile device 120 is only one exampleof the mobile device that may be used with the present system andmethod, and that the mobile device may have more or fewer componentsthan mentioned, may combine two or more components, or a may have adifferent configuration or arrangement of the components. In the presentsystem and method, mobile device 120 may be implemented with anycomputing device that includes geolocation functionality and is not solarge that it is very inconvenient to move it from one location toanother. Thus, mobile device 120 is not restricted to a smartphone orother hand-held device, and may include pad or tablet computing devices,smart books, net books, laptops, and even larger computing devices withgeolocation functionality that may be moved from one location to anotherwithout significant inconvenience.

FIG. 3B shows an illustration of a mobile device 120 displaying anotherinterface object 320, input request 320′″. Input request 320′″ will varybased upon the input data required under the permit at thesite/location. As discussed above, only a limited number of inputrequests 320′″ may be presented on mobile device 120 at a time, whichcan help assure compliance with obtaining all necessary data to bereported.

FIG. 3C shows an illustration of a mobile device 120 displaying anotherinterface object 320, warning 320″″. Warning 320″″ may be presented whenan input data/value exceeds a permitted parameter. Warning 320″″ may beaccompanied by the sending of a message to the appropriatepersons/agencies and can serve to warn the compliance officer of acondition that may warrant immediate action by the officer.

FIG. 4 is a process diagram of an exemplary monitoring, comparing, andreporting system 400 according to an embodiment of the presentinvention.

At step 404, a location of the computing device is determined. Thelocation of the computing device may be determined as discussed above,for example, by using geolocation module 204. The location may refer to,for example, an area (such as a lagoon or stream), a building, acomplete organization site, or a partial site.

At step 408, a permit associated with the location is determined. Incertain circumstances, more than one permit may be associated with agiven location. In this situation, process 400 may request complianceofficer input at step 412 so as to determine the appropriate permittinginformation for the process.

At step 416, the permit is evaluated to determine the inputs required tosatisfactorily complete monitoring compliance. This evaluation takesinto account the possibility that certain monitoring requirements of agiven permit may not be required at the same intervals as otherrequirements. For example, and as shown in FIG. 3, certain parametersare measured daily, others are measured weekly, and others are measuredmonthly.

At step 420, an input request is displayed for the compliance officerbased upon the determinations made at step 416. In this embodiment, thecompliance officer is required to input data relevant to the inputrequest before being allowed to review and provide input to anotherinput request. In another embodiment, more than one input request may bemade at step 420.

At step 424, a determination as to whether any additional measurementsare required under the permit. If additional measurements are required,the process proceeds to step 428A, if not, the process proceeds to step428B. In both 428A and 428B, the input data from the compliance officeris compared to the permitted value (such as a discharge value). If theinput data exceeds the permitted value, process 400 proceeds to eitherstep 432A or 432B (respectively), which reports the non-compliance. Inan embodiment, steps 432A or 432B evaluates what type of reporting needsto be performed. For example, for some types of substances, occasionallyexceeding a permitted value may be allowable, while in other instances,such as toxic chemicals, there may be no allowance for exceeding thepermitted value. These different situations may result in differentreporting requirements that dictate who needs to be contacted, how soonthey need to be contacted, and other immediate/subsequent steps to take.

If the input data does not exceed the permitted value, process 400returns to step 420, which returns another input request from the samepermit until there are no further items subject to monitoring under thepermit.

Once all permit inputs are completed by the compliance officer, the datais presented for authentication at step 436, by for example,authentication module 228. Authentication ensures that the data issubmitted to the designated agency by a person with the right andresponsibility to do so. At step 440 the authenticated data is reportedout to the designated agency.

Optionally, at step 444, a prediction as to the likelihood of anenforcement action is provided. A prediction can be determined asprovided above with regards to prediction module 216. The prediction mayalso be a part of any report generated at step 432A or 432B.

Process 400 may be repeated for any number of permits at a given site.

FIG. 5 shows a diagrammatic representation of one embodiment ofcomputing system 100 in the exemplary form of a system 500, e.g.,computing device 104 or mobile device 120, within which a set ofinstructions for causing a processor 504 to perform any one or more ofthe aspects and/or methodologies, such as process 400, of the presentdisclosure. It is also contemplated that multiple computing devices,such as computing device 104, or mobile devices 120, or combinations ofcomputing devices and mobile devices, may be utilized to implement aspecially configured set of instructions for causing PCS 200 to performany one or more of the aspects and/or methodologies of the presentdisclosure.

System 500 can also include a memory 508 that communicate with eachother, and with other components, via a bus 512. Bus 512 may include anyof several types of bus structures including, but not limited to, amemory bus, a memory controller, a peripheral bus, a local bus, and anycombinations thereof, using any of a variety of bus architectures.

Memory 508 may include various components (e.g., machine readable media)including, but not limited to, a random access memory component (e.g., astatic RAM “SRAM”, a dynamic RAM “DRAM”, etc.), a read only component,and any combinations thereof. In one example, a basic input/outputsystem 516 (BIOS), including basic routines that help to transferinformation between elements within system 500, such as during start-up,may be stored in memory 508. Memory 508 may also include (e.g., storedon one or more machine-readable media) instructions (e.g., software) 520embodying any one or more of the aspects and/or methodologies of thepresent disclosure. In another example, memory 508 may further includeany number of program modules including, but not limited to, anoperating system, one or more application programs, other programmodules, program data, and any combinations thereof.

System 500 may also include a storage device 524, such as, but notlimited to, the machine readable storage medium described above. Storagedevice 524 may be connected to bus 512 by an appropriate interface (notshown). Example interfaces include, but are not limited to, SCSI,advanced technology attachment (ATA), serial ATA, universal serial bus(USB), IEEE 1394 (FIREWIRE), and any combinations thereof. In oneexample, storage device 524 (or one or more components thereof) may beremovably interfaced with system 500 (e.g., via an external portconnector (not shown)). Particularly, storage device 524 and anassociated machine-readable medium 528 may provide nonvolatile and/orvolatile storage of machine-readable instructions, data structures,program modules, and/or other data for system 500. In one example,software 520 may reside, completely or partially, withinmachine-readable medium 528. In another example, software 520 mayreside, completely or partially, within processor 504.

System 500 may also include an input device 532. In one example, a userof system 500 may enter commands and/or other information into system500, for example using input device 208, via input device 532. Examplesof an input device 532 include, but are not limited to, an alpha-numericinput device (e.g., a keyboard), a pointing device, a joystick, agamepad, an audio input device (e.g., a microphone, a voice responsesystem, etc.), a cursor control device (e.g., a mouse), a touchpad, anoptical scanner, a video capture device (e.g., a still camera, a videocamera), touchscreen, and any combinations thereof. Input device 532 maybe interfaced to bus 512 via any of a variety of interfaces (not shown)including, but not limited to, a serial interface, a parallel interface,a game port, a USB interface, a FIREWIRE interface, a direct interfaceto bus 512, and any combinations thereof. Input device 532 may include atouch screen interface that may be a part of or separate from display536, discussed further below. Input device 532 may be utilized as a userselection device for selecting one or more graphical representations ina graphical interface as described above.

A user may also input commands and/or other information to system 500via storage device 524 (e.g., a removable disk drive, a flash drive,etc.) and/or network interface device 540. A network interface device,such as network interface device 540 may be utilized for connectingsystem 500 to one or more of a variety of networks, such as network 544,and one or more remote devices 548 connected thereto. Examples of anetwork interface device include, but are not limited to, a networkinterface card (e.g., a mobile network interface card, a LAN card), amodem, and any combination thereof. Examples of a network include, butare not limited to, a wide area network (e.g., the Internet, anenterprise network), a local area network, a telephone network, a datanetwork associated with a telephone/voice provider, a direct connectionbetween two computing devices, and any combinations thereof. A network,such as network 544, may employ a wired and/or a wireless mode ofcommunication. In general, any network topology may be used. Information(e.g., data, software 520, etc.) may be communicated to and/or fromsystem 500 via network interface device 540.

System 500 may further include a video display adapter 552 forcommunicating a displayable image to a display device, such as displaydevice 536. Examples of a display device include, but are not limitedto, a liquid crystal display (LCD), a cathode ray tube (CRT), a plasmadisplay, a light emitting diode (LED) display, and any combinationsthereof. In addition to a display device, a system 500 may include oneor more other peripheral output devices including, but not limited to,an audio speaker, a printer, and any combinations thereof. Suchperipheral output devices may be connected to bus 512 via a peripheralinterface 556. Examples of a peripheral interface include, but are notlimited to, a serial port, a USB connection, a FIREWIRE connection, aparallel connection, and any combinations thereof.

Exemplary embodiments have been disclosed above and illustrated in theaccompanying drawings. It will be understood by those skilled in the artthat various changes, omissions and additions may be made to that whichis specifically disclosed herein without departing from the spirit andscope of the present invention.

What is claimed is:
 1. A permit compliance system for monitoring asite's compliance with one or more permits limiting or controlling theactivities and/or discharges from the site, the permit compliance systemcomprising: a mobile compliance device having a processor and anon-transitory computer readable medium in communication with saidprocessor, wherein said non-transitory computer readable mediumincludes: an input module configured to: determine a location of saidmobile compliance device and one or more permit limitations related tosaid location, wherein each of said one or more permit limitationsincludes a permitted discharge value; and receive data for each of saidone or more permit limitations representing an actual discharge; acomparison module configured to determine a difference between saidactual discharge with said permitted discharge value; and a predictionmodule configured to determine a likelihood of an enforcement actionbased upon said difference.
 2. A permit compliance system according toclaim 1, wherein said input module is further configured to present eachof said one or more permit limitations as determined by the location ofsaid mobile device.
 3. A permit compliance system according to claim 1,wherein said input module is further configured such that no alterationsto received data are permitted after said mobile device is no longer atthe location of the received data.
 4. A permit compliance systemaccording to claim 1, wherein said comparison module is furtherconfigured to determine an extent of said actual discharge based uponsaid difference.
 5. A permit compliance system according to claim 4,wherein said comparison module is further configured to provide a set ofremedial instructions to a user of the system, wherein said set ofinstructions are based upon said extent of said actual discharge.
 6. Apermit compliance system according to claim 4, wherein said likelihoodis based upon two or more considerations, said considerations including:a number of exceeded permit limitations; said extent; an amount of timeof said exceeded permit limitation; a toxicity or dangerousness of saidexceeded permit limitation; how often enforcement actions are takenagainst industries related to the site; how often the site has had anenforcement action brought against it; number of enforcement actions inthe surrounding geographical area; number of enforcement actions takenin that jurisdiction for similar noncompliance; cost of enforcementactions for similar noncompliance as said exceeded permit limitation;and the speed with which the site remedies said exceeded permitlimitation.
 7. A permit compliance system according to claim 1, whereinsaid prediction module is further configured to provide a cost ofnon-remedial action related to said actual discharge.
 8. A permitcompliance system according to claim 1, wherein said non-transitorycomputer readable medium further includes a reporting module, saidreporting module configured to evaluate said difference and to transmitinformation related to said actual discharge to certain site personnelneeding to know said information.
 9. A permit compliance systemaccording to claim 8, wherein said reporting module is furtherconfigured to access a database that includes information related tocompliance credits.
 10. A permit compliance system according to claim 9,wherein said reporting module is further configured to purchase saidcompliance credits related to said actual discharge and said difference.11. A permit compliance system for monitoring, reporting, and complyingwith permit limitations related to a site or a permitted discharge, thepermit compliance system comprising: a mobile compliance device having aprocessor and a non-transitory computer readable medium in communicationwith said processor, said mobile compliance device configured to receiveinformation related to a discharge; a database in communication withsaid mobile compliance device, said database including: one or morepermits related to the site or the permitted discharge; records relatingto past discharge activity at the site; and compliance credits earned orowned by the site; and a reporting system in communication with saidmobile compliance device and said database, said reporting systemconfigured to: determine the existence of a discharge event; determineremedial steps based on said discharge event; and transmit informationrelated to said discharge event and said remedial steps.
 12. A permitcompliance system according to claim 11, wherein said non-transitorycomputer readable medium includes an input module configured todetermine a location of said mobile compliance device and one or morepermits related to said location.
 13. A permit compliance systemaccording to claim 12, wherein said non-transitory computer readablemedium includes a comparison module configured to determine a differencebetween said discharge with a permitted discharge value.
 14. A permitcompliance system according to claim 13, wherein said non-transitorycomputer readable medium includes a prediction module configured todetermine a likelihood of an enforcement action based upon saiddifference.
 15. A permit compliance system according to claim 11,wherein said reporting system includes a comparison module configured todetermine a difference between said discharge with a permitted dischargevalue.
 16. A permit compliance system according to claim 15, whereinsaid non-transitory computer readable medium includes a predictionmodule configured to determine a likelihood of an enforcement actionbased upon said difference.
 17. A permit compliance system according toclaim 11, wherein said results system is further configured to determinea cost of non-remedial action related to said discharge event.
 18. Apermit compliance system according to claim 11, wherein said reportingsystem is further configured to include a reporting module, saidreporting module being further configured to access said database thatincludes information related to compliance credits.
 19. A permitcompliance system according to claim 18, wherein said reporting moduleis further configured to purchase said compliance credits related tosaid actual discharge and said difference.
 20. A method of limiting anorganization's exposure to violations of a permit having permitteddischarge values comprising: receiving, as an input, information relatedto a discharge at the organization; comparing the discharge to thepermitted discharge value contained within the permit regulating theorganization; determining the extent to which the discharge exceeds thepermitted discharge; predicting a risk value by evaluating saiddetermining in conjunction with one or more of: a number of exceededpermit limitations; the extent; an amount of time the extent; a toxicityor dangerousness of the extent; how often enforcement actions are takenagainst industries related to the organization; how often theorganization has had an enforcement action brought against it; number ofenforcement actions in the surrounding geographical area; number ofenforcement actions taken in that jurisdiction for similarnoncompliance; cost of enforcement actions for similar noncompliance asthe extent; and the speed with which the organization remedies theextent; and minimizing the organization's exposure based upon saidevaluating.